Camera user interface with recording space management

ABSTRACT

The present disclosure generally relates to user interfaces for managing recording space for visual media. A computer system displays a camera preview and a recording space affordance that, when selected, initiates performing an operation associated with recording space available for recording media captured by the one or more cameras.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationSer. No. 63/255,654, entitled “CAMERA USER INTERFACE WITH RECORDINGSPACE MANAGEMENT,” filed on Oct. 14, 2021. The content of thisapplication is hereby incorporated by reference in its entirety.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for managing recording space forvisual media.

BACKGROUND

Computer systems store files in memory, such as video files recordedusing a camera. Memory is limited and files that are larger than theavailable memory cannot be stored.

BRIEF SUMMARY

Some techniques for managing recording space for visual media usingelectronic devices, however, are generally cumbersome and inefficient.For example, some existing techniques use a complex and time-consuminguser interface, which may include multiple key presses or keystrokes.For example, some existing techniques require a user to provide inputsto transition from a camera interface to access a different interface tosee memory usage/availability information, provide additional inputs toaccess an interface for deleting files, whereby the user providesadditional inputs to identify which files should be deleted, and thenproviding inputs to transition back to the camera interface. Existingtechniques require more time than necessary, wasting user time anddevice energy. This latter consideration is particularly important inbattery-operated devices.

Accordingly, the present technique provides electronic devices withfaster, more efficient methods and interfaces for managing recordingspace for visual media. Such methods and interfaces optionallycomplement or replace other methods for managing recording space forvisual media. The present methods and interfaces reduce the cognitiveburden on a user and produce a more efficient human-machine interface.For battery-operated computing devices, such methods and interfacesconserve power and increase the time between battery charges.

In accordance with some embodiments, a method performed at a computersystem having one or more cameras, wherein the computer system is incommunication with a display generation component and one or more inputdevices, is described. The method comprises: displaying, via the displaygeneration component, a camera user interface, wherein displaying thecamera user interface includes concurrently displaying: a camera previewthat includes a representation of one or more objects in a field-of-viewof a first camera of the one or more cameras; and a recording spaceaffordance that, when selected, initiates performing an operationassociated with recording space available for recording media capturedby the one or more cameras; receiving, via the one or more inputdevices, input corresponding to selection of the recording spaceaffordance; and in response to receiving the input corresponding toselection of the recording space affordance, performing the operationassociated with changing an amount of recording space available forrecording media captured by the one or more cameras.

In accordance with some embodiments, a non-transitory computer-readablestorage medium storing one or more programs configured to be executed byone or more processors of a computer system having one or more camerasand that is in communication with a display generation component and oneor more input devices is described. The one or more programs includinginstructions for: displaying, via the display generation component, acamera user interface, wherein displaying the camera user interfaceincludes concurrently displaying: a camera preview that includes arepresentation of one or more objects in a field-of-view of a firstcamera of the one or more cameras; and a recording space affordancethat, when selected, initiates performing an operation associated withrecording space available for recording media captured by the one ormore cameras; receiving, via the one or more input devices, inputcorresponding to selection of the recording space affordance; and inresponse to receiving the input corresponding to selection of therecording space affordance, performing the operation associated withchanging an amount of recording space available for recording mediacaptured by the one or more cameras.

In accordance with some embodiments, a transitory computer-readablestorage medium storing one or more programs configured to be executed byone or more processors of a computer system having one or more camerasand that is in communication with a display generation component and oneor more input devices is described. The one or more programs includinginstructions for: displaying, via the display generation component, acamera user interface, wherein displaying the camera user interfaceincludes concurrently displaying: a camera preview that includes arepresentation of one or more objects in a field-of-view of a firstcamera of the one or more cameras; and a recording space affordancethat, when selected, initiates performing an operation associated withrecording space available for recording media captured by the one ormore cameras; receiving, via the one or more input devices, inputcorresponding to selection of the recording space affordance; and inresponse to receiving the input corresponding to selection of therecording space affordance, performing the operation associated withchanging an amount of recording space available for recording mediacaptured by the one or more cameras.

In accordance with some embodiments, a computer system having one ormore cameras and that is configured to communicate with a displaygeneration component and one or more input devices is described. Thecomputer system includes one or more processors; and memory storing oneor more programs configured to be executed by the one or moreprocessors. The one or more programs including instructions for:displaying, via the display generation component, a camera userinterface, wherein displaying the camera user interface includesconcurrently displaying: a camera preview that includes a representationof one or more objects in a field-of-view of a first camera of the oneor more cameras; and a recording space affordance that, when selected,initiates performing an operation associated with recording spaceavailable for recording media captured by the one or more cameras;receiving, via the one or more input devices, input corresponding toselection of the recording space affordance; and in response toreceiving the input corresponding to selection of the recording spaceaffordance, performing the operation associated with changing an amountof recording space available for recording media captured by the one ormore cameras.

In accordance with some embodiments, a computer system having one ormore cameras and that is configured to communicate with a displaygeneration component and one or more input devices is described. Thecomputer system includes means for displaying, via the displaygeneration component, a camera user interface, wherein displaying thecamera user interface includes concurrently displaying: a camera previewthat includes a representation of one or more objects in a field-of-viewof a first camera of the one or more cameras; and a recording spaceaffordance that, when selected, initiates performing an operationassociated with recording space available for recording media capturedby the one or more cameras; means for receiving, via the one or moreinput devices, input corresponding to selection of the recording spaceaffordance; and means for, in response to receiving the inputcorresponding to selection of the recording space affordance, performingthe operation associated with changing an amount of recording spaceavailable for recording media captured by the one or more cameras.

In accordance with some embodiments, a computer program product,comprising one or more programs configured to be executed by one or moreprocessors of a computer system having one or more cameras and that isin communication with a display generation component and one or moreinput devices is described. The one or more programs includinginstructions for: displaying, via the display generation component, acamera user interface, wherein displaying the camera user interfaceincludes concurrently displaying: a camera preview that includes arepresentation of one or more objects in a field-of-view of a firstcamera of the one or more cameras; and a recording space affordancethat, when selected, initiates performing an operation associated withrecording space available for recording media captured by the one ormore cameras; receiving, via the one or more input devices, inputcorresponding to selection of the recording space affordance; and inresponse to receiving the input corresponding to selection of therecording space affordance, performing the operation associated withchanging an amount of recording space available for recording mediacaptured by the one or more cameras.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods andinterfaces for managing recording space for visual media, therebyincreasing the effectiveness, efficiency, and user satisfaction withsuch devices. Such methods and interfaces may complement or replaceother methods for managing recording space for visual media.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 6A-6R illustrate exemplary user interfaces for managing memory, inaccordance with some embodiments.

FIG. 7 is a flow diagram illustrating a method for managing memory, inaccordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for managing memory. Appropriate memory managementenables the electronic device to use memory more efficiently, providesthe user with feedback about the availability memory, and reduces theneed for users to provide inputs to manage memory. Such techniques canreduce the cognitive burden on a user who use electronic devices,thereby enhancing productivity. Further, such techniques can reduceprocessor and battery power otherwise wasted on redundant user inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description ofexemplary devices for performing the techniques for managing eventnotifications. FIGS. 6A-6R illustrate exemplary user interfaces formanaging memory, in accordance with some embodiments. FIG. 7 is a flowdiagram illustrating a method for managing memory, in accordance withsome embodiments. The user interfaces in FIGS. 6A-6R are used toillustrate the processes described below, including the processes inFIG. 7 .

The processes described below enhance the operability of the devices andmake the user-device interfaces more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) through various techniques,including by providing improved visual feedback to the user, reducingthe number of inputs needed to perform an operation, providingadditional control options without cluttering the user interface withadditional displayed controls, performing an operation when a set ofconditions has been met without requiring further user input, and/oradditional techniques. These techniques also reduce power usage andimprove battery life of the device by enabling the user to use thedevice more quickly and efficiently.

In addition, in methods described herein where one or more steps arecontingent upon one or more conditions having been met, it should beunderstood that the described method can be repeated in multiplerepetitions so that over the course of the repetitions all of theconditions upon which steps in the method are contingent have been metin different repetitions of the method. For example, if a methodrequires performing a first step if a condition is satisfied, and asecond step if the condition is not satisfied, then a person of ordinaryskill would appreciate that the claimed steps are repeated until thecondition has been both satisfied and not satisfied, in no particularorder. Thus, a method described with one or more steps that arecontingent upon one or more conditions having been met could berewritten as a method that is repeated until each of the conditionsdescribed in the method has been met. This, however, is not required ofsystem or computer readable medium claims where the system or computerreadable medium contains instructions for performing the contingentoperations based on the satisfaction of the corresponding one or moreconditions and thus is capable of determining whether the contingencyhas or has not been satisfied without explicitly repeating steps of amethod until all of the conditions upon which steps in the method arecontingent have been met. A person having ordinary skill in the artwould also understand that, similar to a method with contingent steps, asystem or computer readable storage medium can repeat the steps of amethod as many times as are needed to ensure that all of the contingentsteps have been performed.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. In some embodiments, these terms are used to distinguish oneelement from another. For example, a first touch could be termed asecond touch, and, similarly, a second touch could be termed a firsttouch, without departing from the scope of the various describedembodiments. In some embodiments, the first touch and the second touchare two separate references to the same touch. In some embodiments, thefirst touch and the second touch are both touches, but they are not thesame touch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad). In some embodiments, the electronic deviceis a computer system that is in communication (e.g., via wirelesscommunication, via wired communication) with a display generationcomponent. The display generation component is configured to providevisual output, such as display via a CRT display, display via an LEDdisplay, or display via image projection. In some embodiments, thedisplay generation component is integrated with the computer system. Insome embodiments, the display generation component is separate from thecomputer system. As used herein, “displaying” content includes causingto display the content (e.g., video data rendered or decoded by displaycontroller 156) by transmitting, via a wired or wireless connection,data (e.g., image data or video data) to an integrated or externaldisplay generation component to visually produce the content.

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs (such ascomputer programs (e.g., including instructions)) and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2 ). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, depth camera controller 169,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input control devices 116. The other input control devices116 optionally include physical buttons (e.g., push buttons, rockerbuttons, etc.), dials, slider switches, joysticks, click wheels, and soforth. In some embodiments, input controller(s) 160 are, optionally,coupled to any (or none) of the following: a keyboard, an infrared port,a USB port, and a pointer device such as a mouse. The one or morebuttons (e.g., 208, FIG. 2 ) optionally include an up/down button forvolume control of speaker 111 and/or microphone 113. The one or morebuttons optionally include a push button (e.g., 206, FIG. 2 ). In someembodiments, the electronic device is a computer system that is incommunication (e.g., via wireless communication, via wiredcommunication) with one or more input devices. In some embodiments, theone or more input devices include a touch-sensitive surface (e.g., atrackpad, as part of a touch-sensitive display). In some embodiments,the one or more input devices include one or more camera sensors (e.g.,one or more optical sensors 164 and/or one or more depth camera sensors175), such as for tracking a user's gestures (e.g., hand gestures and/orair gestures) as input. In some embodiments, the one or more inputdevices are integrated with the computer system. In some embodiments,the one or more input devices are separate from the computer system. Insome embodiments, an air gesture is a gesture that is detected withoutthe user touching an input element that is part of the device (orindependently of an input element that is a part of the device) and isbased on detected motion of a portion of the user's body through the airincluding motion of the user's body relative to an absolute reference(e.g., an angle of the user's arm relative to the ground or a distanceof the user's hand relative to the ground), relative to another portionof the user's body (e.g., movement of a hand of the user relative to ashoulder of the user, movement of one hand of the user relative toanother hand of the user, and/or movement of a finger of the userrelative to another finger or portion of a hand of the user), and/orabsolute motion of a portion of the user's body (e.g., a tap gesturethat includes movement of a hand in a predetermined pose by apredetermined amount and/or speed, or a shake gesture that includes apredetermined speed or amount of rotation of a portion of the user'sbody).

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad is, optionally, a touch-sensitive surface that isseparate from touch screen 112 or an extension of the touch-sensitivesurface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more depth camera sensors175. FIG. 1A shows a depth camera sensor coupled to depth cameracontroller 169 in I/O subsystem 106. Depth camera sensor 175 receivesdata from the environment to create a three dimensional model of anobject (e.g., a face) within a scene from a viewpoint (e.g., a depthcamera sensor). In some embodiments, in conjunction with imaging module143 (also called a camera module), depth camera sensor 175 is optionallyused to determine a depth map of different portions of an image capturedby the imaging module 143. In some embodiments, a depth camera sensor islocated on the front of device 100 so that the user's image with depthinformation is, optionally, obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay and to capture selfies with depth map data. In some embodiments,the depth camera sensor 175 is located on the back of device, or on theback and the front of the device 100. In some embodiments, the positionof depth camera sensor 175 can be changed by the user (e.g., by rotatingthe lens and the sensor in the device housing) so that a depth camerasensor 175 is used along with the touch screen display for both videoconferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer and a GPS(or GLONASS or other global navigation system) receiver for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3 )stores device/global internal state 157, as shown in FIGS. 1A and 3 .Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, 1M 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs (such as computer programs(e.g., including instructions)), procedures, or modules, and thusvarious subsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. For example, video player module is,optionally, combined with music player module into a single module(e.g., video and music player module 152, FIG. 1A). In some embodiments,memory 102 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 102 optionally stores additionalmodules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3 ) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit or a higher level object from which application 136-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 190 includes one or more of: data updater 176, object updater177, GUI updater 178, and/or event data 179 received from event sorter170. Event handler 190 optionally utilizes or calls data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orcomputer programs (e.g., sets of instructions or including instructions)need not be implemented as separate software programs (such as computerprograms (e.g., including instructions)), procedures, or modules, andthus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. In some embodiments, memory370 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 370 optionally stores additionalmodules and data structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3 ) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3 ) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including processes 700 (FIG.7 ). A computer-readable storage medium can be any medium that cantangibly contain or store computer-executable instructions for use by orin connection with the instruction execution system, apparatus, ordevice. In some examples, the storage medium is a transitorycomputer-readable storage medium. In some examples, the storage mediumis a non-transitory computer-readable storage medium. The non-transitorycomputer-readable storage medium can include, but is not limited to,magnetic, optical, and/or semiconductor storages. Examples of suchstorage include magnetic disks, optical discs based on CD, DVD, orBlu-ray technologies, as well as persistent solid-state memory such asflash, solid-state drives, and the like. Personal electronic device 500is not limited to the components and configuration of FIG. 5B, but caninclude other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, or device 500.

FIGS. 6A-6R illustrate exemplary user interfaces for managing memory, inaccordance with some embodiments. The user interfaces in these figuresare used to illustrate the processes described below, including theprocesses in FIG. 7 .

FIG. 6A illustrates computer system 600 displaying user interface 610 ofa camera application on display 602 of computer system 600. Computersystem 600 optionally includes some or all the features of devices 100,300, and/or 500. The camera application is in a video recording mode, asindicated by mode selector 610G, but is not currently recording. In someembodiments, user interface 610 is displayed as a result of starting thecamera application or switching from another application to displayingthe user interface of the camera application in video recording mode. Insome embodiments, user interface 610 is displayed as a result ofchanging the mode of the camera application, such as by using modeselector 610G, to the video recording mode from another mode (e.g., froma photo capture mode and/or from a portrait capture mode). In someembodiments, the photo capture mode is used to capture a still imageand/or a fixed-duration video (e.g., a video with a predefinedduration).

At FIG. 6A, camera viewfinder 610A is showing a field-of-view of one ormore cameras of computer system 600, particularly a skateboarding scene.At FIG. 6A, the flash is disabled, as indicated by flash indicator 610B,high quality recording is disabled, as indicated by quality indicator610C, recording is not in progress, as indicator by recording timer610D, HD resolution and 30 frames-per-second are selected, as indicatedby resolution indicator 610E. Zoom option 610F enables (e.g., via touchinputs and/or air gestures) zooming in and out camera viewfinder 610A,shutter button 610H enables (e.g., via touch inputs and/or air gestures)starting and stopping video recordings, and camera selector 6101 enables(e.g., via touch inputs and/or air gestures) changing the camera(s)(e.g., among front camera and/or back camera) used to display thecontent of viewfinder 610A.

Videos recorded while high quality recording is enabled take morestorage space as compared to videos recorded while high qualityrecording is disabled. For example, a 30 second HD resolution, 30 FPSrecording using high quality recording may take 50%, 75%, or 200% morestorage space than the same 30 second HD resolution, 30 FPS recordingthat does not use the high quality recording feature. For anotherexample, a 30 second 4K resolution, 30 FPS recording using high qualityrecording may take 50%, 75%, or 200% more storage space than the same 30second 4K resolution, 30 FPS recording that does not use the highquality recording feature. For another example, a 30 second 4Kresolution, 60 FPS recording using high quality recording may take 50%,75%, or 200% more storage space than the same 30 second 4K resolution,60 FPS recording that does not use the high quality recording feature.However, videos recorded using the high quality recording feature havehigher quality (e.g., are near-lossless, have a reduced degree ofcompression, and/or have higher bitrates) and are thereforeadvantageous. In some embodiments, when the high quality recordingfeature is enabled, the computer system uses a lossless or near-losslesscodec for video recording. In some embodiments, when the high qualityrecording feature is not enabled, the computer system does not use thelossless or near-lossless codec for video recording. In someembodiments, when the high quality recording feature is enabled, thecomputer system encodes and stores video using a high bitrate and/orhigh quality video codec such as Apple ProRes (e.g., ProRes 422 orProRes 4444) or CineForm. Additional information regarding ProRes isavailable at support.apple.com/en-us/HT202410. In some embodiments, whenthe high quality recording feature is not enabled, the computer systemencodes and stores video using a lower bitrate (e.g., a highlycompressed and or highly lossy) video codec such as H.264 or H.265/HEVC.

At FIG. 6A, max recording time indicator 620A and resource managementoption 620B are not displayed because the high quality recording featureis not enabled. In some embodiments, max recording time indicator 620Ais not displayed when the high quality recording feature is not enabledbecause running out of memory is rarely an issue when the feature is notin use. At FIG. 6A, computer system 600 does not display max recordingtime indicator 620A and resource management option 620B (see, e.g., FIG.6E) even when other options (e.g., resolution, frame rate, and/or flash)because the high quality recording feature is not enabled. At FIG. 6A,computer system 600 detects tap input 650A on quality indicator 610C.

At FIG. 6B, in response to detecting tap input 650A on quality indicator610C, computer system 600 enables the high quality recording feature andupdates quality indicator 610C to indicate that the high qualityrecording feature is enabled (and, accordingly, that videos will berecorded using the high quality feature). In response to detecting tapinput 650A, computer system 600 also displays max recording timeindicator 620A, which indicates a maximum amount of time (e.g., inminutes and/or in seconds) of video that can be recorded with thecurrent video recording settings (e.g., high quality recording, HDresolution, and 30 FPS). In some embodiments, the maximum amount of timeof video that can be recorded is based on available (e.g., unused) localmemory at the computer system. In some embodiments, the maximum amountof minutes of video that can be recorded is based on available memory atan external computer system (e.g., at a server connected via a wirelessnetwork connection). In some embodiments, max recording time indicator620A is overlaid on viewfinder 610A (and, in some embodiments, contentof viewfinder 610A is visible through portions of the indicator). Insome embodiments, computer system 600 displays max recording timeindicator 620A when not recording while the high quality recordingfeature is enabled, regardless of the amount of time of video that canbe recorded (e.g., based on available memory). At FIG. 6B, computersystem 600 does not display resource management option 620B as part ofuser interface 610 because the amount of time of video that can berecorded (e.g., 60 minutes, as indicated by max recording time indicator620A) exceeds a threshold recording duration (e.g., 10 minutes, 15minutes, or 30 minutes), which in this example is 15 minutes. At FIG.6B, computer system 600 detects tap input 650B on resolution indicator610E.

At FIG. 6C, in response to detecting tap input 650B on resolutionindicator 610E, computer system 600 changes the resolution at whichvideos will be recorded from high definition (HD) to 4K and updatesresolution indicator 610E to reflect the 4K setting. In response todetecting tap input 650B on resolution indicator 610E, computer system600 also updates max recording time indicator 620A to indicate themaximum amount of time of video that can be recorded with the currentvideo recording settings (e.g., high quality recording, 4K resolution,and 30 FPS). Because 4K recording consumes more memory per minute ascompared to HD recording, max recording time indicator 620A indicates areduced maximum amount of time of 18 minutes at FIG. 6C. At FIG. 6C,while not recording, computer system 600 displays the max recording timeindicator 620A because the high quality recording feature is enabled andcomputer system 600 does not display resource management option 620Bbecause the amount of time of video that can be recorded (e.g., 18minutes) exceeds the threshold recording duration (e.g., 10 minutes, 15minutes, or 30 minutes), which in this example is 15 minutes (e.g., theamount of recording time available is more than 15 minutes). At FIG. 6C,while not recording, although the high quality recording feature isenabled, computer system 600 does not automatically start clearingmemory (e.g., deleting files and/or removing cached files) because theamount of time of video that can be recorded (e.g., 18 minutes) exceedsthe threshold memory clearing duration (e.g., 1 minute, 2 minutes, or 3minutes), which in this example is 2 minutes (e.g., the amount ofrecording time available is more than 2 minutes). However, if the changefrom HD resolution to 4K resolution had caused the maximum amount oftime of video that can be recorded to drop below the threshold memoryclearing duration, computer system 600 would have automatically startedclearing memory, as further described, for example, with respect to FIG.6O.

At FIG. 6C, tap input 652A on flash indicator 610B would toggle (e.g.,enable) the flash, tap input 652B on resolution indicator 610E wouldchange the recording resolution (e.g., back to HD, thereby increasingthe max recording time), tap input 652C would cause computer system 600to focus on an object (e.g., the rail on top of the ramp) displayed inviewfinder 610A at the location at which tap input 652C was received(without clearing memory, as discussed with respect to tap input 654C atFIG. 6G), tap input 652D would cause computer system 600 to focus on anobject (e.g., the side of the ramp) displayed in viewfinder 610A at thelocation at which tap input 652D was received, tap input 652E on zoomoption 610F would cause computer system 600 to change a zoom level(e.g., from 1× zoom to 2× zoom) in viewfinder 610A, tap input 652F oncamera selector 6101 would change viewfinder 610A from a first set ofone or more cameras (e.g., back camera) to a second set of one or morecameras (e.g., front camera) of computer system 600, and tap input 652Hon quality indicator 610C would disable the high quality recordingfeature, thereby causing computer system 600 to cease displaying maxrecording time indicator 620A. At FIG. 6C, computer system 600 detectstap input 652G on shutter button 610H.

At FIG. 6D, in response to detecting tap input 652G on shutter button610H, computer system 600 begins video recording (e.g., capturing motionpicture and corresponding audio), as indicated by updated shutter button610H and progression of recording timer 610D, using the high qualityfeature. At FIG. 6D, while recording video using the high qualityfeature, computer system 600 does not display max recording timeindicator 620A (e.g., overlaid on viewfinder 610A (and, in someembodiments, content of viewfinder 610A is visible through portions ofthe indicator)) because the amount of time of video that can be recorded(e.g., 16 minutes because 18 minutes were available and 2 minutes havebeen recorded thus far) exceeds a threshold duration (e.g., same ordifferent from the threshold recording duration, 9 minutes, 10 minutes,15 minutes, or 25 minutes), which in this example is 15 minutes. At FIG.6D, while recording video using the high quality feature, computersystem 600 does not display resource management option 620B because theamount of time of video that can be recorded (e.g., 16 minutes) exceedsthe threshold recording duration (e.g., 10 minutes, 15 minutes, or 30minutes), which in this example is 15 minutes.

At FIG. 6E, computer system 600 continues to record video, as indicatedby shutter button 610H and progression of recording timer 610D, usingthe high quality feature. At FIG. 6E while recording video using thehigh quality feature, computer system 600 displays max recording timeindicator 620A (e.g., overlaid on viewfinder 610A (and, in someembodiments, content of viewfinder 610A is visible through portions ofthe indicator)) because the amount of remaining time of video that canbe recorded (e.g., 14 minutes because 18 minutes were available and 4minutes have been recorded thus far) does not exceed the thresholdduration (e.g., same or different from the threshold recording duration,9 minutes, 10 minutes, 15 minutes, or 25 minutes), which in this exampleis 15 minutes. At FIG. 6E, while recording video using the high qualityfeature, computer system 600 displays resource management option 620Bbecause the amount of remaining time of video that can be recorded(e.g., 14 minutes) does not exceed the threshold recording duration(e.g., 10 minutes, 15 minutes, or 30 minutes), which in this example is15 minutes. At FIG. 6E, activating resource management option 620B wouldcause computer system 600 to start clearing memory (e.g., deleting filesand/or removing cached files), as discussed, for example, in furtherdetail with respect to FIGS. 6I-6J. In some embodiments, resourcemanagement option 620B is not displayed during recording regardless ofthe amount of remaining time of video that can be recorded.

At FIG. 6F, computer system 600 continues to record video, as indicatedby shutter button 610H and progression of recording timer 610D, usingthe high quality feature. At FIG. 6F, while recording video using thehigh quality feature, computer system 600 displays max recording timeindicator 620A (e.g., overlaid on viewfinder 610A (and, in someembodiments, content of viewfinder 610A is visible through portions ofthe indicator)) because the amount of remaining time of video that canbe recorded (e.g., 12 minutes because 18 minutes were available and 6minutes have been recorded thus far) does not exceed the thresholdduration (e.g., same or different from the threshold recording duration,9 minutes, 10 minutes, 15 minutes, or 25 minutes), which in this exampleis 15 minutes. At FIG. 6F, while recording video using the high qualityfeature, computer system 600 displays resource management option 620Bbecause the amount of remaining time of video that can be recorded(e.g., 12 minutes) does not exceed the threshold recording duration(e.g., 10 minutes, 15 minutes, or 30 minutes), which in this example is15 minutes. At FIG. 6F, activating resource management option 620B wouldcause computer system 600 to start clearing memory (e.g., deleting filesand/or removing cached files), as discussed, for example, in furtherdetail with respect to FIGS. 6I-6J. In some embodiments, resourcemanagement option 620B is not displayed during recording regardless ofthe amount of remaining time of video that can be recorded. At FIG. 6F,computer system 600 detects tap input 650C on shutter button 610H.

At FIG. 6G, in response to detecting tap input 650C on shutter button610H, computer system 600 ceases recording the video, as indicated byupdated shutter button 610H and recording timer 610D. At FIG. 6G, whilenot recording video and with the high quality feature enabled, computersystem 600 displays max recording time indicator 620A (e.g., overlaid onviewfinder 610A (and, in some embodiments, content of viewfinder 610A isvisible through portions of the indicator)) because the amount ofremaining time of video that can be recorded (e.g., 12 minutes) does notexceed the threshold duration, which in this example is 15 minutes(e.g., the amount of recording time available is less than 15 minutes).At FIG. 6G, while not recording video and with the high quality featureenabled, computer system 600 displays resource management option 620Bbecause the amount of remaining time of video that can be recorded(e.g., 12 minutes) does not exceed the threshold recording duration,which in this example is 15 minutes (e.g., the amount of recording timeavailable is less than 15 minutes). In some embodiments where resourcemanagement option 620B is not displayed during recording using the highquality feature regardless of the amount of remaining time of video thatcan be recorded, resource management option 620B is newly displayed whenrecording stops and the amount of remaining time of video that can berecorded does not exceed the threshold recording duration, as shown inFIG. 6G.

In some embodiments, as illustrated in FIG. 6G, computer system 600optionally displays (e.g., overlaid on viewfinder 610A (and, in someembodiments, content of viewfinder 610A is visible through portions ofnotification 610J)) notification 610J that includes an (e.g., estimatedand/or calculated) amount of time it will take to clear an (e.g.,estimated and/or calculated) amount of memory to enable recording of anadditional (e.g., estimated and/or calculated) amount (e.g., 10 mins) ofvideo with the current video settings. In some embodiments, notification610J includes an amount of time it will take to clear some memory and anamount of additional time (and/or total time) that will be available asa result of clearing the memory. In some embodiments, notification 610Jis displayed concurrently with resource management option 620B. In someembodiments, notification 610J is optionally displayed concurrently withresource management option 620B when not recording, but is not displayedcurrently with resource management option 620B during recording (e.g.,is displayed in the user interfaces of FIGS. 6I, 6O-6Q, but is notdisplayed the user interfaces of FIGS. 6E-6F). In some embodiments,notification 610J is not displayed during recording and is not displayedwhile not recording, regardless of the amount of time of video that canbe recorded. In some embodiments, notification 610J is not displayedwhen the high quality feature is not enabled, regardless of the amountof time of video that can be recorded.

At FIG. 6G, tap input 654A on flash indicator 610B would toggle (e.g.,enable) the flash, tap input 654B on resolution indicator 610E wouldchange the recording resolution (e.g., back to HD, thereby increasingthe max recording time), tap input 654C (though at the same location onthe touch-sensitive surface/touchscreen as tap input 652C) would causecomputer system 600 to start clearing memory (e.g., deleting filesand/or removing cached files) (without performing a focus operation),tap input 654D would cause computer system 600 to focus on an object(e.g., the side of the ramp) displayed in viewfinder 610A at thelocation at which tap input 654D was received, tap input 654E on zoomoption 610F would cause computer system 600 to change a zoom level(e.g., from 1× zoom to 2× zoom) in viewfinder 610A, tap input 654F oncamera selector 6101 would change viewfinder 610A from a first set ofone or more cameras (e.g., back camera) to a second set of one or morecameras (e.g., front camera) of computer system 600, tap input 654G onshutter button 610H would start video recording, and tap input 654H onquality indicator 610C would disable the high quality recording feature,thereby causing computer system 600 to cease displaying max recordingtime indicator 620A and cease displaying resource management option620B. At FIG. 6G, computer system 600 detects tap input 650D on photomode of mode selector 610G.

At FIG. 6H, in response to detecting tap input 650D, computer system 600changes modes from video recording mode to photo capture mode, asindicated in updated mode selector 610G. At FIG. 6H, because the cameraapplication is now in photo capture mode (and not in video recordingmode), the high quality feature is not available for use and qualityindicator 610C is not displayed. At FIG. 6H, because the cameraapplication is now in photo capture mode (and not in video recordingmode) and/or because the high quality feature is not available, maxrecording time indicator 620A and resource management option 620B arenot displayed, regardless of the amount of available memory forcapturing photos and regardless of the amount of time of video that canbe recorded using the video recording mode.

At FIG. 6H, tap input 656A on flash indicator 610B would toggle (e.g.,enable) the flash, tap input 656B on fixed-duration video record option610K would enable recording of a fixed-duration video when computersystem 600 detects a tap input on shutter button 610H, tap input 656Cwould cause computer system 600 to focus on an object (e.g., the personon top of the ramp) displayed in viewfinder 610A at the location atwhich tap input 656C was received (without clearing memory, as discussedwith respect to tap input 654C at FIG. 6G), tap input 656D would causecomputer system 600 to focus on an object (e.g., the side of the ramp)displayed in viewfinder 610A at the location at which tap input 656D wasreceived, tap input 656E on zoom option 610F would cause computer system600 to change a zoom level (e.g., from 1× zoom to 2× zoom) in viewfinder610A, tap input 656F on camera selector 6101 would change viewfinder610A from a first set of one or more cameras (e.g., back camera) to asecond set of one or more cameras (e.g., front camera) of computersystem 600, and tap input 656H would not change the state of the highquality recording feature. At FIG. 6H, computer system 600 detects tapinput 650E on video mode of mode selector 610G.

At FIG. 6I, in response to detecting tap input 650E, computer system 600changes modes from photo capture mode to video recording mode, asindicated in updated mode selector 610G. At FIG. 6I, while notrecording, because the camera application is in video recording modewith the high quality feature enabled (as indicated by quality indicator610C) and the amount of remaining time of video that can be recorded(e.g., 12 minutes) does not exceed the threshold duration, which in thisexample is 15 minutes, computer system 600 displays max recording timeindicator 620A (e.g., overlaid on viewfinder 610A (and, in someembodiments, content of viewfinder 610A is visible through portions ofthe indicator)). At FIG. 6I, while not recording video, computer system600 displays resource management option 620B because the high qualityfeature is enabled and the amount of time of video that can be recorded(e.g., 12 minutes) does not exceed the threshold recording duration,which in this example is 15 minutes. In some embodiments, as illustratedin FIG. 6I, computer system 600 optionally displays (e.g., overlaid onviewfinder (and, in some embodiments, content of viewfinder 610A isvisible through portions of notification 610J)) notification 610J thatincludes an (e.g., estimated and/or calculated) amount of time it willtake to clear an (e.g., estimated and/or calculated) amount of memory toenable recording of an additional (e.g., estimated and/or calculated)amount (e.g., 10 mins) of video with the current video settings, asfurther described with respect to FIG. 6G. At FIG. 6I, computer system600 detects tap input 650F on resource management option 620B.

In response to detecting tap input 650F, computer system 600 startsclearing memory (e.g., deleting files and/or removing cached files) tomake additional memory available for video recording and updatesresource management option 620B to indicate that additional memory isbeing made available (without performing a focus operation). At FIG. 6J,as more memory becomes available for video recording, recording timeindicator 620A is updated to reflect the additional available recordingtime (e.g., the max time has increased between FIGS. 6I and 6J from 12minutes to 15 minutes). While computer system 600 is clearing memory,activation of the resource management option 620B would cause computersystem 600 to stop clearing memory.

At FIG. 6K, as more memory becomes available for video recording,recording time indicator 620A is updated to reflect the additionalavailable recording time (e.g., the max time has increased between FIGS.6J and 6K from 15 minutes to 19 minutes). At FIG. 6K, while clearingmemory, computer system 600 detects tap input 650G on resourcemanagement option 620B.

At FIG. 6L, in response to detecting tap input 650G, computer system 600begins cancelling the memory clearing operation and updates resourcemanagement option 620B to indicate that memory clearing is beingcanceled (without performing a focus operation). At FIG. 6M, aftercancellation of memory clearing is complete, computer system 600continues to display max recording time indicator 620A because the highquality recording feature is enabled, regardless of the amount of timeof video that can be recorded (e.g., based on available memory). At FIG.6M, computer system 600 does not display resource management option 620Bas part of user interface 610 because the amount of time of video thatcan be recorded (e.g., 19 minutes, as indicated by max recording timeindicator 620A) exceeds the threshold recording duration (e.g., 10minutes, 15 minutes, or 30 minutes), which in this example is 15minutes. In some embodiments, computer system 600 continues to updatemax recording time indicator 620A while max recording time indicator620A is displayed and as other applications write files to the memory(thereby reducing the amount of memory available for video recording)and/or delete files from memory (thereby increasing the amount of memoryavailable for recording).

At FIG. 6N, computer system 600 has received user input to switch todisplaying an application other than the camera application and,therefore, is no longer displaying the camera application. Instead,computer system 600 is displaying user interface 630 of an applicationfor downloading files. After switching to the application fordownloading files, computer system 600 has downloaded songs, books, tvshows, and movies and saved them in the memory of computer system 600,thereby reducing the amount of memory available for recording videosusing the camera application. At FIG. 6N, while the camera applicationis not displayed, computer system 600 does not automatically clearmemory (e.g., does not delete files and/or remove cached files) to makeadditional memory available for video recording, regardless of theamount of time of video that can be recorded (e.g., based on availablememory) using the camera application. While displaying user interface630 of the application for downloading files, computer system 600receives user input to display the camera application.

At FIG. 6O, in response to receiving the user input to display thecamera application, computer system 600 displays user interface 610 ofthe camera application. Because the newly downloaded files that weresaved to memory have reduced the available memory for video recording to1 minute, computer system 600 displays max recording time indicator 620Awith an indication that only 1 minute of video recording is available.At FIG. 6O, in response to receiving the user input to display thecamera application, because the high quality recording feature isenabled and because the amount of time of video that can be recorded(e.g., 1 minute) does not exceed (e.g., is less than) the thresholdmemory clearing duration, which in this example is 2 minutes, thecomputer system automatically (e.g. without receiving further userinputs) starts clearing memory (e.g., deleting files and/or removingcached files). At FIG. 6O, because the high quality recording feature isenabled and because the amount of time of video that can be recorded(e.g., 1 minute) does not exceeds the threshold memory clearingduration, which in this example is 2 minutes, the computer systemdisables the recording functionality, as indicated by the grayed outshutter button 610H. In some embodiments, clearing memory includesdelete files that were saved to memory by an application other than thecamera application, such as deleting the songs, books, tv shows, and/ormovies saved to memory by the application for downloading files and/ordelete cache files, such as cache files for a web browser, for a mailprogram, and/or for a mapping/navigation program.

At FIG. 6O, tap input 658A on flash indicator 610B would toggle (e.g.,enable) the flash, tap input 658B on resolution indicator 610E wouldchange the recording resolution (e.g., back to HD, thereby increasingthe max recording time) and would enable shutter button 610H for videorecording if the increased max recording time exceeds the thresholdmemory clearing duration, tap input 658C (though at the same location onthe touch-sensitive surface/touchscreen as tap input 652C and tap input654C) on resource management option 620B would cause computer system 600to stop clearing memory (without performing a focus operation), tapinput 658D would cause computer system 600 to focus on an object (e.g.,the side of the ramp) displayed in viewfinder 610A at the location atwhich tap input 658D was received, tap input 658E on zoom option 610Fwould cause computer system 600 to change a zoom level (e.g., from 1×zoom to 2× zoom) in viewfinder 610A, tap input 658F on camera selector6101 would change viewfinder 610A from a first set of one or morecameras (e.g., back camera) to a second set of one or more cameras(e.g., front camera) of computer system 600, tap input 658G (though atthe same location on the touch-sensitive surface/touchscreen as tapinput 652G and tap input 660G) on shutter button 610H would not beginvideo recording because the recording functionality is disabled, asdiscussed above, and tap input 658H on quality indicator 610C woulddisable the high quality recording feature, thereby causing computersystem 600 to cease displaying max recording time indicator 620A andenabling shutter button 610H for video recording.

At FIG. 6P, computer system 600 continues to clear memory if resourcemanagement option 620B is not activated (e.g., a tap input is notreceived on resource management option 620B). As memory is cleared, maxrecording time indicator 620A is updated to indicate the maximum amountof time of video that can be recorded with the current video recordingsettings (e.g., high quality recording, 4K resolution, and 30 FPS). Asshown in FIG. 6P, enough memory has been cleared to enable recording of3 minutes of video with the current video recording settings. Becausethe amount of time of video that can be recorded (e.g., 3 minutes)exceeds the threshold memory clearing duration, computer system 600enables the recording functionality and, optionally, shutter button 610His no longer grayed out.

At FIG. 6P, tap input 660A on flash indicator 610B would toggle (e.g.,enable) the flash, tap input 660B on resolution indicator 610E wouldchange the recording resolution (e.g., back to HD, thereby increasingthe max recording time), tap input 660C (though at the same location onthe touch-sensitive surface/touchscreen as tap input 652C and tap input654C) on resource management option 620B would cause computer system 600to stop clearing memory (without performing a focus operation), tapinput 660D would cause computer system 600 to focus on an object (e.g.,the side of the ramp) displayed in viewfinder 610A at the location atwhich tap input 660D was received, tap input 660E on zoom option 610Fwould cause computer system 600 to change a zoom level (e.g., from 1×zoom to 2× zoom) in viewfinder 610A, tap input 660F on camera selector6101 would change viewfinder 610A from a first set of one or morecameras (e.g., back camera) to a second set of one or more cameras(e.g., front camera) of computer system 600, tap input 660G (though atthe same location on the touch-sensitive surface/touchscreen as tapinput 658G) on shutter button 610H would begin video recording becausethe recording functionality is enabled, and tap input 660H on qualityindicator 610C would disable the high quality recording feature, therebycausing computer system 600 to cease displaying max recording timeindicator 620A. In some embodiments, beginning recording while memory isbeing cleared causes computer system 600 to stop clearing memory. Insome embodiments, beginning recording while memory is being clearedcauses computer system 600 to concurrently clear memory and recordvideo.

Computer system 600 continues to clear memory if resource managementoption 620B is not activated (e.g., a tap input is not received onresource management option 620B). In some embodiments, disabling thehigh quality feature and/or switching to a different mode (e.g., photocapture mode) optionally causes computer system 600 to stop clearingmemory. At FIG. 6Q, computer system 600 has finished clearing memoryand, as a result, max recording time indicator 620A is updated toindicate the maximum amount of time of video that can be recorded withthe current video recording settings (e.g., high quality recording, 4Kresolution, and 30 FPS). As shown in FIG. 6Q, enough memory has beencleared to enable recording of 11 minutes of video with the currentvideo recording settings. At FIG. 6Q, while not recording, because thecamera application is in video recording mode with the high qualityfeature enabled (as indicated by quality indicator 610C) and the amountof remaining time of video that can be recorded (e.g., 11 minutes) doesnot exceed the threshold duration, which in this example is 15 minutes,computer system 600 displays max recording time indicator 620A (e.g.,overlaid on viewfinder 610A (and, in some embodiments, content ofviewfinder 610A is visible through portions of the indicator)). At FIG.6Q, while not recording video, computer system 600 displays resourcemanagement option 620B because the high quality feature is enabled andthe amount of time of video that can be recorded (e.g., 11 minutes) doesnot exceed the threshold recording duration, which in this example is 15minutes. Computer system 600 does not automatically start clearingmemory (e.g., deleting files and/or removing cached files) because theamount of time of video that can be recorded (e.g., 11 minutes) exceedsthe threshold memory clearing duration (e.g., 1 minute, 2 minutes, or 3minutes), which in this example is 2 minutes (e.g., the amount ofrecording time available is more than 2 minutes). However, if arecording option is changed (e.g., higher resolution, higher FPS) tocause the maximum amount of time of video that can be recorded to dropbelow the threshold memory clearing duration, computer system 600 wouldautomatically started clearing memory. At FIG. 6Q, computer system 600detects tap input 650H on photo mode of mode selector 610G.

At FIG. 6R, in response to detecting tap input 650H, computer system 600changes modes from video recording mode to photo capture mode, asindicated in updated mode selector 610G. At FIG. 6R, because the cameraapplication is now in photo capture mode (and not in video recordingmode), the high quality feature is not available for use and qualityindicator 610C is not displayed. At FIG. 6R, because the cameraapplication is now in photo capture mode (and not in video recordingmode) and/or because the high quality feature is not available, maxrecording time indicator 620A and resource management option 620B arenot displayed, regardless of the amount of available memory forcapturing photos and regardless of the amount of time of video that canbe recorded using the video recording mode. At FIG. 6R, computer system600 detects tap input 650I on video mode of mode selector 610G.

As shown in FIG. 6Q, in response to detecting tap input 650I, computersystem 600 changes modes from photo capture mode to video recordingmode, as indicated in updated mode selector 610G. At FIG. 6Q, while notrecording, because the camera application is in video recording modewith the high quality feature enabled (as indicated by quality indicator610C) and the amount of remaining time of video that can be recorded(e.g., 11 minutes) does not exceed the threshold duration, which in thisexample is 15 minutes, computer system 600 displays max recording timeindicator 620A (e.g., overlaid on viewfinder 610A (and, in someembodiments, content of viewfinder 610A is visible through portions ofthe indicator)). At FIG. 6Q, while not recording video, computer system600 displays resource management option 620B because the high qualityfeature is enabled and the amount of time of video that can be recorded(e.g., 11 minutes) does not exceed the threshold recording duration,which in this example is 15 minutes. In some embodiments, as discussedabove, computer system 600 optionally displays (e.g., overlaid onviewfinder (and, in some embodiments, content of viewfinder 610A isvisible through portions of the notification)) a notification (e.g.,notification 610J) that includes an (e.g., estimated and/or calculated)amount of time it will take to clear an (e.g., estimated and/orcalculated) amount of memory to enable recording of an additional (e.g.,estimated and/or calculated) amount (e.g., 10 mins) of video with thecurrent video settings.

In some embodiments, computer system 600 switches to the photo capturemode (e.g., at FIG. 6R) and captures and stores photos in memory thatreduce the available memory space such that the amount of time of videothat can be recorded in the video capture mode using the high qualityfeature does not exceed the threshold memory clearing duration (e.g., 1minute, 2 minutes, or 3 minutes), which in this example is 2 minutes(e.g., the amount of recording time available is below 2 minutes). Insuch circumstances, upon receiving input (e.g., tap input 650I) totransition back to the video capture mode, computer system 600transitions to the video capture mode and, if the high quality featureis enabled, automatically (e.g., without further user inputs) startsclearing memory.

In some embodiments, while in the video capture mode with the highquality feature enabled and displaying user interface 610, computersystem 600 (e.g., applications other than the camera application) storefiles in memory that reduce the available memory space such that theamount of time of video that can be recorded in the video capture modeusing the high quality feature does not exceed the threshold memoryclearing duration (e.g., 1 minute, 2 minutes, or 3 minutes), which inthis example is 2 minutes (e.g., the amount of recording time availabledrops below 2 minutes). In such circumstances, computer system 600automatically (e.g., without further user inputs) starts clearingmemory.

FIG. 7 is a flow diagram illustrating a method for managing memory usinga computer system in accordance with some embodiments. Method 700 isperformed at a computer system (e.g., 100, 300, 500, and/or 600 (e.g., asmartphone or a smartwatch)) having one or more cameras (e.g., one ormore cameras (e.g., dual cameras, triple camera, or quad cameras) on thesame side or on different sides of the computer system (e.g., a frontcamera and/or a back camera)) and that is in communication with adisplay generation component (e.g., a display controller and/or atouch-sensitive display) and one or more input devices (e.g., atouch-sensitive surface and/or a keyboard). Some operations in method700 are, optionally, combined, the orders of some operations are,optionally, changed, and some operations are, optionally, omitted.

As described below, method 700 provides an intuitive way for managingrecording space for visual media. The method reduces the cognitiveburden on a user for managing recording space for visual media, therebycreating a more efficient human-machine interface. For battery-operatedcomputing devices, enabling a user to manage recording space for visualmedia faster and more efficiently conserves power and increases the timebetween battery charges.

The computer system (e.g., 600) displays (702), via the displaygeneration component (e.g., 602), a camera user interface (e.g., 610)(e.g., a user interface associated with (included in, of) a cameraapplication (e.g., an application for capturing media, such as photosand videos)). Displaying the camera user interface (e.g., 610) includesconcurrently displaying: a camera preview (704) (e.g., 610A) (e.g., alive preview of a field-of-view from a camera that updates over time)that includes a representation of one or more objects in a field-of-viewof a first camera of the one or more cameras; and a recording spaceaffordance (706) (e.g., 620B) that, when selected, initiates performingan operation associated with recording space (e.g., storage space on oneor more storage devices (e.g., hard drives, solid state drives, and/orflash drives) of the computer system) available for recording mediacaptured by the one or more cameras (e.g., initiates deleting of cacheddata (e.g., data associated with improving (e.g., improving the speedof) operations (e.g., browsing, data retrieval) of the operating systemand/or one or more applications (e.g., a browser, social media, and/orpodcast application, applications other than the application associatedwith the camera user interface)) and/or initiates cancelling anin-progress deleting of cached data).

The computer system (e.g., 600) receives (708), via the one or moreinput devices, input (e.g., 654C, 650F, 650G, 658C, 660C) correspondingto (e.g., a tap input on, a selection of) selection of the recordingspace affordance (e.g., 620B).

The computer system (e.g., 600), in response to receiving the input(e.g., 654C, 650F, 650G, 658C, 660C) corresponding to selection of therecording space affordance (e.g., 620B), performs (710) the operationassociated with changing an amount of recording space available forrecording media captured by the one or more cameras. Displaying arecording space affordance and performing the operation associated withchanging an amount of recording space available for recording media uponselection of that affordance provides the user with the ability toaffect an amount of recording space available, which can improve theoperation of the camera functionality of the computer system. Improvingthe operation of the camera functionality of the computer systemenhances the operability of the system and makes the user-systeminterfaces more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thesystem). These techniques also reduce power usage and improve batterylife of the system by enabling the user to use the device more quicklyand efficiently. Displaying the recording space affordance concurrentlywith the camera preview in the camera user interface provides the userwith the ability to perform the operation (e.g., an operation to makeadditional recording space available) without having to navigate throughmultiple menus and/or having to navigate away from the live preview,which improves the user's ability to capture camera media of apotentially transient event (e.g., a transient moment/composition).Improving the user's ability to better capture transient events improvesthe operation of the camera functionality of the computer system,enhancing the operability of the system, and making the user-systeminterfaces more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thesystem). These techniques also reduce power usage and improve batterylife of the system by enabling the user to use the device more quicklyand efficiently.

In some embodiments, in accordance with a determination that therecording space available for recording media captured by the one ormore cameras is (e.g., at a time the input corresponding to selection ofthe recording space affordance is received; at a time when the recordingspace affordance is caused to be displayed) greater than a firstthreshold amount (e.g., greater than an amount required to record athreshold amount (e.g., 5, 10, 15, 20, or 30 minutes of video) of media(e.g., video media) at a current camera setting (e.g., HD video, 4Kvideo, video at a 30 frames-per-second, video at 60 frames-per-second,and/or video stored in a first file format (e.g., an uncompressed orless compressed format))) of available space, the operation associatedwith changing an amount of recording space available for recording mediacaptured by the one or more cameras includes increasing (712) (e.g., bydeleting data (e.g., data cached by one or more applications) currentlyoccupying the recording space) the amount of recording space availablefor recording media captured by the one or more cameras (e.g., tap input650F). In accordance with a determination that the recording spaceavailable for recording media captured by the one or more cameras is(e.g., at a time the input corresponding to selection of the recordingspace affordance is received; at a time when the recording spaceaffordance is caused to be displayed) below the threshold amount ofmedia (e.g., video media) at a current camera setting (e.g., HD video,4K video, video at a 30 frames-per-second, video at 60frames-per-second, and/or video stored in a first file format (e.g., anuncompressed or less compressed format)) of available space, theoperation associated with changing an amount of recording spaceavailable for recording media captured by the one or more camerasincludes cancelling (714) an operation (e.g., an in-progress operation)to increase (e.g., by deleting data (e.g., data cached by one or moreapplications) currently occupying the recording space) the amount ofrecording space available for recording media captured by the one ormore cameras (e.g., tap input 650G). Conditionally configuring therecording space affordance to cause performance of an operation toincrease the amount of recording space available for recording mediacaptured by the one or more cameras when the recording space availableis greater than a first threshold amount performs an operation (e.g.,configuring the function of the recording space affordance) when a setof conditions has been met without requiring further user input, and/oradditional techniques and also provides additional control optionswithout cluttering the user interface with additional displayedcontrols.

In some embodiments, the operation associated with changing an amount ofrecording space available for recording media captured by the one ormore cameras includes the computer system (e.g., 600) increasing (e.g.,by deleting data (e.g., data cached by one or more applications)currently occupying the recording space) the amount of recording spaceavailable for recording media captured by the one or more cameras.Displaying recording space affordance concurrently with the camerapreview in the camera user interface provides the user with the abilityto perform an operation to increase the amount of recording spacewithout having to navigate through multiple menus and/or having tonavigate away from the live preview, which improves the user's abilityto capture camera media (or capture a longer duration of media) of apotentially transient event (e.g., a transient moment/composition).Improving the user's ability to better capture transient events improvesthe operation of the camera functionality of the computer system (e.g.,600), enhancing the operability of the system, and making theuser-system interfaces more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the system). These techniques also reducepower usage and improve battery life of the system by enabling the userto use the device more quickly and efficiently.

In some embodiments, while increasing the amount of recording spaceavailable for recording media captured by the one or more cameras is inprogress (e.g., has been initiated but not completed), the computersystem (e.g., 600) displays, via the display generation component, anindication (e.g., a textual (e.g., a percentage) or graphicalrepresentation (e.g., a progress bar; an elapsed time and a remainingtime, and/or an animated spinner)) of progress towards completion ofincreasing the amount of recording space available for recording mediacaptured by the one or more cameras (e.g., 620A, 620B in FIGS. 6I-6K).Displaying the indication of progress towards completion of increasingthe amount of recording space available for recording media captured bythe one or more cameras provides improved visual feedback as to thecurrent progress of the increasing operation.

In some embodiments, while increasing the amount of recording spaceavailable for recording media captured by the one or more cameras is inprogress (e.g., has been initiated but not completed), the computersystem (e.g., 600) receives, via the one or more input devices, a secondinput corresponding to selection of the recording space affordance(e.g., 650G). In some embodiments, the visual appearance of therecording space affordance is different while the operation is inprogress than when the operation is not in progress (e.g., 620B at FIG.6I as compared to 620B in FIGS. 6J-6L). In response to receiving thesecond input (e.g., 650G), the computer system (e.g., 600) cancels(e.g., ceasing or aborting) at least a portion of increasing the amountof recording space available for recording media captured by the one ormore cameras (e.g., as shown in FIG. 6L). In some embodiments,cancelling at least the portion of the increasing operation occurs afterat least a portion of the increasing operation has been completed (e.g.,at least some recording space has been made available). In someembodiments, cancelling at least the portion of the increasing operationincludes reversing at least a portion of the increasing operation thathas been completed (e.g., restoring data that was deleted to make spaceavailable). Cancelling the increasing operation, while in progress, inresponse to a selection of the recording space affordance provides theuser with the ability to cancel the operation, which can improve theoperation of the camera functionality of the computer system. Improvingthe operation of the camera functionality of the computer systemenhances the operability of the system and make the user-system,interfaces more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thesystem). These techniques also reduce power usage and improve batterylife of the system by enabling the user to use the device more quicklyand efficiently.

In some embodiments, after (In some embodiments, while the increasing isin progress) increasing the amount of recording space available forrecording media captured by the one or more cameras is in progress(e.g., has been initiated but not completed), the computer system (e.g.,600) receives, via the one or more input devices, a request (e.g., 660G)to capture media with the one or more cameras (e.g., selection of aphysical or virtual shutter button such as a tap on (e.g., at a locationcorresponding to) a shutter button (e.g., 610H) (e.g., a selectable userinterface object for capturing media)) (in some embodiments, the shutterbutton is displayed concurrently with the recording space affordance).In response to receiving the request to capture media with the one ormore cameras, the computer system (e.g., 600) captures first media (insome embodiments, and recording the first media (e.g., in recordingspace made available via the process of increasing the amount ofrecording space available for recording media captured by the one ormore cameras)).

In some embodiments, the operation associated with changing an amount ofrecording space available for recording media captured by the one ormore cameras includes cancelling an operation (e.g., an in-progressoperation) to increase (e.g., by deleting data (e.g., data cached by oneor more applications) currently occupying the recording space) theamount of recording space available for recording media captured by theone or more cameras. Providing an affordance that cancels an operationto increase the amount of recording space concurrently with the livepreview provides the user with access to a control to cancel theoperation without having to navigate through multiple menus and/orhaving to navigate away from the live preview, which provides enhancedand readily-accessed control options. Providing enhanced andreadily-accessed control options improves the operation of the camerafunctionality of the computer system, enhancing the operability of thesystem and making the user-system interfaces more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the system). These techniques alsoreduce power usage and improve battery life of the system by enablingthe user to use the device more quickly and efficiently.

In some embodiments, prior to receiving the input corresponding toselection of the recording space affordance, the computer system (e.g.,600) detects a first event (e.g., a change in a state of the computersystem; a user input (e.g., an input to enable a specific media capturemode (e.g., a capture mode for HD video, 4K video, video at a 30frames-per-second, video at 60 frames-per-second, and/or video stored ina first file format (e.g., an uncompressed or less compressedformat)))). In response to detecting the first event and in accordancewith a determination that a set of operation initiation criteria aremet, wherein the set of operation initiation criteria includes acriterion that is met when the recording space available for recordingmedia captured by the one or more cameras is less than the secondthreshold amount, the computer system (e.g., 600) initiates (e.g., as inFIG. 6O) the operation to increase the amount of recording spaceavailable for recording media captured by the one or more cameras. Inresponse to detecting the first event and in accordance with adetermination that the set of operation initiation criteria are not met,the computer system (e.g., 600) forgoes initiating (e.g., as in FIGS. 6Band 6I) the operation to increase the amount of recording spaceavailable for recording media captured by the one or more cameras.Initiating the operation to increase the amount of recording spaceavailable for recording media captured by the one or more cameras whenthe set of operation initiation criteria are met performs the operationwhen a set of conditions has been met without requiring further userinput, and/or additional techniques.

In some embodiments, the first event includes transitioning from a firstmedia capture mode (e.g., a camera capture mode (e.g., photo capturemode, a standard video capture mode), as shown in FIGS. 6H-6I) (in someembodiments, the first event is a transition in media capture qualitysettings (e.g., HD to 4K), as shown in FIGS. 6B-6C, a transition inframe rate (e.g., 30 FPS to 60 FPS), and/or a transition in a videocodec (e.g., from a high compression codec (e.g., H.264 or H.265) to alower (or no) compression codec (e.g., ProRes or CineForm))) to a secondmedia capture mode (e.g., a high-definition video capture mode; a videocapture mode that includes storing the captured video in an uncompressedor less compressed format, as shown in FIGS. 6A-6B). Initiating theoperation to increase the amount of recording space available forrecording media captured by the one or more cameras when the mediacapture mode transitions and when the set of operation initiationcriteria are met performs the operation when a set of conditions hasbeen met without requiring further user input, and/or additionaltechniques.

In some embodiments, the operation associated with changing an amount ofrecording space available for recording media captured by the one ormore cameras includes deleting at least some data (e.g., podcasts,applications, music, media (e.g., television shows and/or movies)recorded at one or more external devices and transmitted to the computersystem; cached data) that is not camera data (e.g., data that is notdata captured by the one or more cameras, and/or is not video or imagedata from a captured media collection associated with the user).

In some embodiments, the operation associated with changing an amount ofrecording space available for recording media captured by the one ormore cameras includes deleting data (e.g., previously captured videosand/or photos) that was previously captured by the one or more camerasand that meets a set of backup criteria (e.g., the data has been backedup to one or more storage devices (e.g., cloud storage on one or moreremote servers and/or storage of an external drive) other than storageof the computer system). Deleting data when that data meets a set ofbackup criteria performs an operation when a set of conditions has beenmet without requiring further user input, and/or additional techniques,reduces the risk of deleting data that is unrecoverable, and reduces theneed for the user to manually confirm that data has been backed upelsewhere and therefore can be safely deleted.

In some embodiments, displaying the camera user interface (e.g., 610)includes the computer system (e.g., 600) displaying, concurrently withthe camera preview (e.g., 610A) and the recording space affordance(e.g., 620B), an indication (e.g., 620A) (e.g., a textual (e.g., “15minutes remaining”) and/or graphical indication) of an amount of timeavailable to record and store, in the recording space, media captured bythe one or more cameras. Displaying an indication of an amount of timeavailable to record and store, in the recording space, media captured bythe one or more cameras provides the user with improved visual feedbackas to the amount of recording space that is available.

In some embodiments, the indication (e.g., 620A) of the amount of timeavailable to record and store, in the recording space, media captured bythe one or more cameras is based on (e.g., varies depending on a bitrate(e.g., an amount of data stored per unit time (e.g., per minute) of acurrent capture mode)) a current media capture mode of the computersystem (e.g., for a 30 FPS capture mode the time is 30 minutes and for a60 FPS capture mode at the same resolution the time is 15 minutes; forHD the time is 40 minutes and for 4K, it is 10 minutes; for ahigh-compression codec (e.g., H.265) the time is 30 minutes and for alow compression codec (e.g., ProRes), the time is 10 minutes).Displaying an indication of an amount of time available to record andstore, in the recording space, media captured by the one or more camerasthat is based on the current media capture mode provides the user withimproved visual feedback as to the amount of recording space that isavailable, specifically for the current mode.

In some embodiments, in accordance with a determination that the amountof time available to record and store, in the recording space, mediacaptured by the one or more cameras is a first value (e.g., a valueabove a threshold value (e.g., greater than 2, 5, or 10 minutes)), therecording space affordance (in some embodiments, and/or the indicationof an amount of time available to record and store) has a first visualappearance (e.g., 620B at FIG. 6K) (e.g., a first color scheme; a firstsize; a first fill pattern); and in accordance with a determination thatthe amount of time available to record and store, in the recordingspace, media captured by the one or more cameras is a second value(e.g., a value below a threshold value), the recording space affordancehas a second visual appearance (e.g., 620B at FIG. 6O), different fromthe first visual appearance. Displaying the recording space affordancewith different visual appearances based on the amount of time availableto record and store provides the user with improved visual feedback asto the available amount of recording space.

In some embodiments, while a first amount of recording space isavailable for recording media captured by the one or more cameras andwhile the indication of the amount of time available to record andstore, in the recording space, media captured by the one or more camerasindicates a first amount of time (e.g., “10 minutes remaining” or “15minutes remaining”) (e.g., 620A at FIG. 6J), the computer system (e.g.,600) determines that the amount of recording space available forrecording media captured by the one or more cameras has increased to asecond amount of recording space. In response to determining that theamount of recording space available for recording media captured by theone or more cameras has increased to the second amount of recordingspace, the computer system (e.g., 600) updates the indication of theamount of time available (e.g., 620A at FIG. 6K) to record and store, inthe recording space, media captured by the one or more cameras toindicate a second amount of time (e.g., “20 minutes remaining” or “25minutes remaining”), greater than the first amount of time. Updating theindication of an amount of time available to record and store, in therecording space, media captured by the one or more cameras as more spacebecomes available provides the user with improved visual feedback as tochange in the amount of recording space that is available.

In some embodiments, while a third amount of recording space isavailable for recording media captured by the one or more cameras andwhile the indication of the amount of time available to record andstore, in the recording space, media captured by the one or more camerasindicates a third amount of time (e.g., 620A at FIG. 6E) (e.g., “15minutes remaining” or “20 minutes remaining”), the computer system(e.g., 600) captures first media via the one or more cameras and storingthe first media in the recording space. In response to capturing thefirst media via the one or more cameras and storing the first media inthe recording space, the computer system (e.g., 600) updates theindication of the amount of time available to record and store, in therecording space, media captured by the one or more cameras to indicate afourth amount of time (e.g., 620A at FIG. 6F), less than the thirdamount of time (e.g., “14 minutes remaining” or “10 minutes remaining”).Updating the indication of an amount of time available to record andstore, in the recording space, media captured by the one or more camerasas media is captured and space is consumed provides the user withimproved visual feedback as to change in the amount of recording spacethat is available.

In some embodiments, the recording space affordance is displayed whilecapture of media via the one or more cameras is not occurring (e.g.,prior to the start of a media capture operation) (e.g., 620B at FIG.6C). Displaying the recording space affordance while capture of mediavia the one or more cameras is not occurring provides the user withimproved visual feedback as to the availability of the operationassociated with the recording space affordance at that point in time.

In some embodiments, the recording space affordance is displayed whilecapture of media via the one or more cameras is occurring (e.g.,ongoing; during a media capture operation). Displaying the recordingspace affordance while capture of media via the one or more cameras isoccurring provides the user with improved visual feedback as to theavailability of the operation associated with the recording spaceaffordance at that point in time.

In some embodiments, during ongoing capture of media with the one ormore cameras of the device (e.g., while displaying the camera userinterface in a currently recording mode of operation) and while therecording space affordance is not displayed (e.g., at FIG. 6D), thecomputer system determines that the recording space available forrecording media captured by the one or more cameras has fallen below athird threshold amount (e.g., an amount required to record a thresholdamount (e.g., 15 minutes of video, 20 minutes of video, or 30 minutes ofvideo) of media (e.g., video media) at a current camera setting (e.g.,HD video, 4K video, video at a 30 frames-per-second, video at 60frames-per-second, and/or video stored in a first file format (e.g., anuncompressed or less compressed format))); in response to determiningthat the recording space available for recording media captured by theone or more cameras has fallen below the third threshold amount, thecomputer system (e.g., 600) displays (e.g., initially displaying) therecording space affordance (in some embodiments, the recording spaceaffordance is displayed during media capture when the amount ofrecording space falls below a threshold level) (e.g., 620B at FIG. 6E).Initially displaying the recording space affordance while capture ofmedia via the one or more cameras is occurring and when available spacedrops below the threshold amount provides the user with improved visualfeedback as to the change in available space and performs an operation(e.g., displaying the recording space affordance) when a set ofconditions has been met without requiring further user input, and/oradditional techniques.

In some embodiments, the recording space affordance (e.g., 620B) isoverlaid on the camera preview (e.g., 610A) (e.g., overlaid on at leasta portion of a representation of the field of view of the one or morecameras). Overlaying the recording space affordance on the camerapreview conserves space in the camera user interface and makes theaffordance available without the user having to navigate throughmultiple menus and/or away from the live preview, which improves theuser's ability to capture camera media of a potentially transient event(e.g., a transient moment/composition). Improving the user's ability tobetter capture transient events improves the operation of the camerafunctionality of the computer system, enhancing the operability of thesystem, and making the user-system interfaces more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the system). These techniques alsoreduce power usage and improve battery life of the system by enablingthe user to use the device more quickly and efficiently.

In some embodiments, displaying the camera user interface (e.g., 610)includes the computer system displaying, concurrently with the camerapreview (e.g., 610A) and the recording space affordance (e.g., 620B), amedia capture affordance (e.g., 610H) (e.g., a virtual shutter button)that, when selected, initiates capture of media (e.g., video and/orphotos) via the one or more cameras. Displaying media capture affordanceconcurrently with the recording space affordance makes the recordingspace affordance available concurrently with the media captureaffordance without the user having to navigate through multiple menusand/or away from the live preview, which improves the user's ability tocapture camera media of a potentially transient event (e.g., a transientmoment/composition). Improving the user's ability to better capturetransient events improves the operation of the camera functionality ofthe computer system, enhancing the operability of the system, and makingthe user-system interfaces more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the system). These techniques also reducepower usage and improve battery life of the system by enabling the userto use the device more quickly and efficiently.

In some embodiments, the computer system (e.g., 600) receives, via theone or more input devices, input (e.g., 652G) corresponding to the mediacapture affordance (e.g., 610H). In response to receiving the input(e.g., 652G) corresponding to the media capture affordance (e.g., 610H),the computer system initiates the capture of media (e.g., capture ofvideo; capture of one or more photos) via the one or more cameras.Providing the media capture affordance and initiating capture of mediaon selection of the affordance provides the user with improved visualfeedback as to how to initiate media capture.

In some embodiments, the computer system (e.g., 600) displays, in thecamera user interface (e.g., 610), a media capture affordance (e.g.,610H) (e.g., a virtual shutter button) (e.g., an affordance that, whenenabled/selectable and selected, initiates capture of media (e.g., videoand/or photos) via the one or more cameras) that includes: in accordancewith a determination that the recording space available for recordingmedia captured by the one or more cameras is above a fourth thresholdamount (e.g., an amount required to record a threshold amount (e.g., 2minutes of video, 5 minutes of video, 10 minutes of video) of media(e.g., video media) at a current camera setting (e.g., HD video, 4Kvideo, video at a 30 frames-per-second, video at 60 frames-per-second,and/or video stored in a first file format (e.g., an uncompressed orless compressed format))), the computer system displaying the mediacapture affordance in a first visual state (e.g., 610H at FIG. 6P)(e.g., non-greyed out), wherein the media capture affordance isselectable (e.g., is enabled or is available for use) while in the firstvisual state; and in accordance with a determination that the recordingspace available for recording media captured by the one or more camerasis below the fourth threshold amount, the computer system displaying themedia capture affordance in a second visual state (e.g., 610H at FIG.6O) (e.g., greyed out), wherein the media capture affordance is notselectable (e.g., is not enabled or is not available for use to initiatemedia capture) while in the second visual state. Conditionallydisplaying the media capture affordance in a first or second visualstate that is connected to selectability of the affordance and is basedon whether available recording space is above or below a fourththreshold amount provides users with improved visual feedback as to theavailable amount of space and performs an operation (e.g., altering themedia capture affordance) when a set of conditions has been met withoutrequiring further user input, and/or additional techniques.

In some embodiments, while the media capture affordance is displayed inthe second visual state (e.g., 610H at FIG. 6O), the computer system(e.g., 600) determines that the amount of recording space available forrecording media captured by the one or more cameras has increased abovethe fourth threshold amount. In response to determining that the amountof recording space available for recording media captured by the one ormore cameras has increased above the fourth threshold amount, thecomputer system (e.g., 600) updates the media capture affordance fromthe second visual state to the first visual state (e.g., 610H at FIG.6P). Modifying the visual state and selectability state of the mediacapture affordance when the available recording space increases abovethe fourth threshold value provides users with improved visual feedbackas to the available amount of space and performs an operation (e.g.,altering the media capture affordance) when a set of conditions has beenmet without requiring further user input, and/or additional techniques.

In some embodiments, while the media capture affordance is displayed inthe second visual state (e.g., 610H at FIG. 6O), the computer system(e.g., 600) detects a request (e.g., 658H, 658B) to modify one or moremedia capture settings (e.g., file size or the amount of data that isstored (e.g., per unit time) while capturing media) (in someembodiments, the media capture bitrate is changed when one or morequality settings of the captured video are changed (e.g., resolution(e.g., via 610E), framerate (e.g., via 610E), data storage format,and/or video codec (e.g., via 610C))). In response to detecting therequest to modify the one or more media capture settings: the computersystem modifies the one or more media settings, wherein modifying theone or more media settings reduces the bitrate of captured media; andupdates the media capture affordance from the second visual state to thefirst visual state (e.g., 610H at FIG. 6P). Modifying the visual stateand selectability state of the media capture affordance when the mediacapture settings are modified provides users with improved visualfeedback as to modification to the media settings and performs anoperation (e.g., altering the media capture affordance) when a set ofconditions has been met without requiring further user input, and/oradditional techniques.

In some embodiments, displaying the camera user interface (e.g., 610)includes the computer system displaying, concurrently with the camerapreview (e.g., 610A) and the recording space affordance (e.g., 620B), aset of one or more media capture setting affordances (e.g., affordancesfor changing the media capture quality (e.g., 610C), media captureresolution (e.g., 610E), media capture bitrate (e.g., 610C); mediacapture framerate (e.g., 610E); zoom level (e.g., 610F); and/or flashstate (e.g., 610B)). Displaying a set of one or more media capturesetting affordances concurrently with the recording space affordance andthe live preview provides the user with access to the settingsaffordances without the user having to navigate through multiple menusand/or away from the live preview, which improves the user's ability tocapture camera media of a potentially transient event (e.g., a transientmoment/composition). Improving the user's ability to better capturetransient events improves the operation of the camera functionality ofthe computer system, enhancing the operability of the system, and makingthe user-system interfaces more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the system). These techniques also reducepower usage and improve battery life of the system by enabling the userto use the device more quickly and efficiently.

In some embodiments, the set of one or more media capture settingaffordances includes a first media capture setting affordance (e.g.,610C and/or 610E) that, when selected, changes the media capture bitrate(e.g., file size or the amount of data that is stored (e.g., per unittime) while capturing media) (in some embodiments, the media capturebitrate is changed when one or more quality settings of the capturedvideo are changed (e.g., resolution, framerate)).

In some embodiments, the set of one or more media capture settingaffordances includes two or more different media capture settingaffordances independently selected from the group consisting of: a mediacapture setting affordance (e.g., 610C) that modifies a media codecsetting (an uncompressed media codec or a low compression media codec(e.g., a codec (e.g., ProRes (e.g., ProRes 4444 or ProRes 4444 XQ) orCineForm) having a bitrate that is higher than compressed or morecompressed media codec (e.g., H.264 or H.265))), a media capture settingaffordance that modifies a frame rate setting (e.g., 30 FPS, 60 FPS),and a media capture setting affordance that modifies a pixel densitysetting (e.g., 610E) (e.g., video resolution setting (e.g., HDresolution, a 4K resolution)).

In some embodiments, while the computer system (e.g., 600) is in a thirdmedia capture mode (e.g., a photo capture mode) (e.g., at FIG. 6H) andwhile the recording space affordance (e.g., 620B) is not displayed, thecomputer system (e.g., 600) detects a request (e.g., 650E) to transitionto a fourth media capture mode (e.g., a video capture mode). In responseto the request to transition to the fourth media capture mode: thecomputer system (e.g., 600) transitions to the fourth media capture mode(e.g., at FIG. 6I); and displays the recording space affordance (e.g.,620B) (e.g., as part of the camera user interface). Displaying therecording space affordance when transitioning to the fourth mediacapture mode provides the user with improved visual feedback as to thecurrent mode and the relevance of the recording space affordance to thefourth media capture mode and provides additional control options (e.g.,when in the fourth media capture mode) without cluttering the userinterface with additional displayed controls (e.g., when in the thirdmedia capture mode). Displaying the recording space affordance with thelive preview on transitioning into the fourth media capture mode providethe user with access to the recording space affordance in an appropriatemode without the user having to navigate through multiple menus and/oraway from the live preview, which improves the user's ability to capturecamera media of a potentially transient event (e.g., a transient momentor composition). Improving the user's ability to better capturetransient events improves the operation of the camera functionality ofthe computer system, enhancing the operability of the system, and makingthe user-system interfaces more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the system). These techniques also reducepower usage and improve battery life of the system by enabling the userto use the device more quickly and efficiently.

In some embodiments, the computer system (e.g., 600) displays a secondcamera user interface (e.g., a second instance of the camera userinterface displayed at a different time). Displaying the second camerauser interface includes: in accordance with a determination that therecording space available for recording media captured by the one ormore cameras is below a fifth threshold amount (e.g., an amount requiredto record a threshold amount (e.g., 10 minutes of video, 15 minutes ofvideo, 20 minutes of video) of media (e.g., video media) at a currentcamera setting (e.g., HD video, 4K video, video at a 30frames-per-second, video at 60 frames-per-second, and/or video stored ina first file format (e.g., an uncompressed or less compressed format))),the computer system displaying the camera preview concurrently with therecording space affordance (e.g., at FIG. 6I); and in accordance with adetermination that the recording space available for recording mediacaptured by the one or more cameras is above the fifth threshold amount,the computer system displaying the camera preview without the recordingspace affordance (e.g., at FIG. 6B). Conditionally displaying therecording space affordance based on whether available recording space isabove or below a fifth threshold amount provides users with improvedvisual feedback as to modification to the media settings, performs anoperation (e.g., displaying the media capture affordance) when a set ofconditions has been met without requiring further user input, and/oradditional techniques, and provides additional control options withoutcluttering the user interface with additional displayed controls (e.g.,when the control may be less relevant).

In some embodiments, displaying the camera preview without the recordingspace affordance includes the computer system (e.g., 600) displaying,concurrently with the camera preview (e.g., 610A), a second indication(e.g., 620A) (e.g., a textual (e.g., “15 minutes remaining”) and/orgraphical indication) of an amount of time available to record andstore, in the recording space, media captured by the one or morecameras. Displaying the second indication of the amount of timeavailable to record and store, in the recording space, media captured bythe one or more cameras without displaying the recording spaceaffordance provides improved visual feedback as to the amount of timeavailable to record and store, in the recording space, media captured bythe one or more cameras.

In some embodiments, the recording space affordance (e.g., 620B), whendisplayed in the second camera user interface, is displayed at a firstlocation in the second camera user interface. While displaying thesecond camera user interface, the computer system (e.g., 600) receives,via the one or more input devices an input (e.g., 650F, 650G, 652C)corresponding to the first location. In response to receiving the inputcorresponding to the first location: in accordance with a determinationthat the recording space affordance is currently displayed in the secondcamera user interface (e.g., as in FIGS. 6I and 6K), the computer system(e.g., 600) performs the operation associated with changing an amount ofrecording space available for recording media captured by the one ormore cameras; and in accordance with a determination that the recordingspace affordance is not currently displayed in the second camera userinterface (e.g., as in FIG. 6C), the computer system performs a cameraoperation (e.g., set focus point (e.g., via tap input (e.g., 652C and/or656C) at the first location), set auto exposure point (e.g., via atap-and-drag gesture), select subject to emphasize (e.g., viatap-and-hold (e.g., 652C and/or 656C) on a subject), and/or set exposurecompensation) that does not include performing the operation associatedwith changing an amount of recording space available for recording mediacaptured by the one or more cameras. Performing the operation associatedwith changing an amount of recording space available for recording mediacaptured by the one or more cameras or performing a camera operation,depending on whether the recording space affordance is currentlydisplayed performs a specific operation when a set of conditions hasbeen met without requiring further user input, and/or additionaltechniques.

In some embodiments, the recording space affordance (e.g., 620B) isdisplayed concurrently with an indication (e.g., 610J) (e.g., a textual(e.g., “get 15 extra minutes”) and/or graphical indication) of anadditional amount of time available to record and store, in therecording space, media captured by the one or more cameras that would bemade available by performing the operation associated with changing anamount of recording space available for recording media captured by theone or more cameras. In some embodiments, the indication also includesan indication of an amount of time (e.g., estimated time (e.g., 5seconds, 10 seconds, 20 seconds, or 30 seconds) that is required tocomplete the operation, once the operation is initiated). Displaying anindication of an additional amount of time available to record andstore, in the recording space, media captured by the one or more camerasthat would be made available by performing the operation associated withchanging an amount of recording space available for recording mediacaptured by the one or more cameras provides the user with improvedvisual feedback as to how much time would be made available by theoperation and a much time is required to complete the operation.Displaying an indication of how much additional recording time would bemade available (and, in some embodiments, that includes an indication ofan amount of time needed to complete the operation) assists the userwith capture camera media of a potentially transient event (e.g., atransient moment/composition of a certain expected duration). Improvingthe user's ability to better capture transient events improves theoperation of the camera functionality of the computer system, enhancingthe operability of the system, and making the user-system interfacesmore efficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the system).These techniques also reduce power usage and improve battery life of thesystem by enabling the user to use the device more quickly andefficiently.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

As described above, one aspect of the present technology is thegathering and use of data available from various sources to improvemanagement of recording space for visual media. The present disclosurecontemplates that in some instances, this gathered data may includepersonal information data that uniquely identifies or can be used tocontact or locate a specific person. Such personal information data caninclude demographic data, location-based data, telephone numbers, emailaddresses, twitter IDs, home addresses, data or records relating to auser's health or level of fitness (e.g., vital signs measurements,medication information, exercise information), date of birth, or anyother identifying or personal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used todetermine which content to delete. Accordingly, use of such personalinformation data enables users to have calculated control of the memory.Further, other uses for personal information data that benefit the userare also contemplated by the present disclosure.

The present disclosure contemplates that the entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities shouldimplement and consistently use privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining personal information data private andsecure. Such policies should be easily accessible by users, and shouldbe updated as the collection and/or use of data changes. Personalinformation from users should be collected for legitimate and reasonableuses of the entity and not shared or sold outside of those legitimateuses. Further, such collection/sharing should occur after receiving theinformed consent of the users. Additionally, such entities shouldconsider taking any needed steps for safeguarding and securing access tosuch personal information data and ensuring that others with access tothe personal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations. For instance, in the US,collection of or access to certain health data may be governed byfederal and/or state laws, such as the Health Insurance Portability andAccountability Act (HIPAA); whereas health data in other countries maybe subject to other regulations and policies and should be handledaccordingly. Hence different privacy practices should be maintained fordifferent personal data types in each country.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof memory management, the present technology can be configured to allowusers to select to “opt in” or “opt out” of participation in thecollection of personal information data during registration for servicesor anytime thereafter. In addition to providing “opt in” and “opt out”options, the present disclosure contemplates providing notificationsrelating to the access or use of personal information. For instance, auser may be notified upon downloading an app that their personalinformation data will be accessed and then reminded again just beforepersonal information data is accessed by the app.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing specific identifiers (e.g., date of birth,etc.), controlling the amount or specificity of data stored (e.g.,collecting location data a city level rather than at an address level),controlling how data is stored (e.g., aggregating data across users),and/or other methods.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, content can beselected for deletion by inferring preferences based on non-personalinformation data or a bare minimum amount of personal information, suchas the content being requested by the device associated with a user,other non-personal information available to the system, or publiclyavailable information.

What is claimed is:
 1. A computer system having one or more cameras and that is configured to communicate with a display generation component and one or more input devices, comprising: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: displaying, via the display generation component, a camera user interface, wherein displaying the camera user interface includes concurrently displaying: a camera preview that includes a representation of one or more objects in a field-of-view of a first camera of the one or more cameras; and a recording space affordance that, when selected, initiates performing an operation associated with recording space available for recording media captured by the one or more cameras; receiving, via the one or more input devices, input corresponding to selection of the recording space affordance; and in response to receiving the input corresponding to selection of the recording space affordance, performing the operation associated with changing an amount of recording space available for recording media captured by the one or more cameras.
 2. The computer system of claim 1, wherein: in accordance with a determination that the recording space available for recording media captured by the one or more cameras is greater than a first threshold amount of available space, the operation associated with changing an amount of recording space available for recording media captured by the one or more cameras includes increasing the amount of recording space available for recording media captured by the one or more cameras; and in accordance with a determination that the recording space available for recording media captured by the one or more cameras is below the first threshold amount of available space, the operation associated with changing an amount of recording space available for recording media captured by the one or more cameras includes cancelling an operation to increase the amount of recording space available for recording media captured by the one or more cameras.
 3. The computer system of claim 1, wherein the operation associated with changing an amount of recording space available for recording media captured by the one or more cameras includes increasing the amount of recording space available for recording media captured by the one or more cameras.
 4. The computer system of claim 2, the one or more programs further including instructions for: while increasing the amount of recording space available for recording media captured by the one or more cameras is in progress, displaying, via the display generation component, an indication of progress towards completion of increasing the amount of recording space available for recording media captured by the one or more cameras.
 5. The computer system of claim 2, the one or more programs further including instructions for: while increasing the amount of recording space available for recording media captured by the one or more cameras is in progress, receiving, via the one or more input devices, a second input corresponding to selection of the recording space affordance; and in response to receiving the second input, cancelling at least a portion of increasing the amount of recording space available for recording media captured by the one or more cameras.
 6. The computer system of claim 2, the one or more programs further including instructions for: after increasing the amount of recording space available for recording media captured by the one or more cameras is in progress, receiving, via the one or more input devices, a request to capture media with the one or more cameras; and in response to receiving the request to capture media with the one or more cameras, capturing first media.
 7. The computer system of claim 1, wherein the operation associated with changing an amount of recording space available for recording media captured by the one or more cameras includes cancelling an operation to increase the amount of recording space available for recording media captured by the one or more cameras.
 8. The computer system of claim 1, the one or more programs further including instructions for: prior to receiving the input corresponding to selection of the recording space affordance, detecting a first event; and in response to detecting the first event: in accordance with a determination that a set of operation initiation criteria are met, wherein the set of operation initiation criteria includes a criterion that is met when the recording space available for recording media captured by the one or more cameras is less than a second threshold amount, initiating the operation to increase the amount of recording space available for recording media captured by the one or more cameras; and in accordance with a determination that the set of operation initiation criteria are not met, forgoing initiating the operation to increase the amount of recording space available for recording media captured by the one or more cameras.
 9. The computer system of claim 8, wherein the first event includes transitioning from a first media capture mode to a second media capture mode.
 10. The computer system of claim 1, wherein the operation associated with changing an amount of recording space available for recording media captured by the one or more cameras includes deleting at least some data that is not camera data.
 11. The computer system of claim 1, wherein the operation associated with changing an amount of recording space available for recording media captured by the one or more cameras includes deleting data that was previously captured by the one or more cameras and that meets a set of backup criteria.
 12. The computer system of claim 1, wherein displaying the camera user interface includes displaying, concurrently with the camera preview and the recording space affordance, an indication of an amount of time available to record and store, in the recording space, media captured by the one or more cameras.
 13. The computer system of claim 12, wherein the indication of the amount of time available to record and store, in the recording space, media captured by the one or more cameras is based on a current media capture mode of the computer system.
 14. The computer system of claim 1, wherein: in accordance with a determination that the amount of time available to record and store, in the recording space, media captured by the one or more cameras is a first value, the recording space has a first visual appearance; and in accordance with a determination that the amount of time available to record and store, in the recording space, media captured by the one or more cameras is a second value, the recording space affordance has a second visual appearance, different from the first visual appearance.
 15. The computer system of claim 12, the one or more programs further including instructions for: while a first amount of recording space is available for recording media captured by the one or more cameras and while the indication of the amount of time available to record and store, in the recording space, media captured by the one or more cameras indicates a first amount of time, determining that the amount of recording space available for recording media captured by the one or more cameras has increased to a second amount of recording space; and in response to determining that the amount of recording space available for recording media captured by the one or more cameras has increased to the second amount of recording space, updating the indication of the amount of time available to record and store, in the recording space, media captured by the one or more cameras to indicate a second amount of time, greater than the first amount of time.
 16. The computer system of claim 12, the one or more programs further including instructions for: while a third amount of recording space is available for recording media captured by the one or more cameras and while the indication of the amount of time available to record and store, in the recording space, media captured by the one or more cameras indicates a third amount of time, capturing first media via the one or more cameras and storing the first media in the recording space; and in response to capturing the first media via the one or more cameras and storing the first media in the recording space, updating the indication of the amount of time available to record and store, in the recording space, media captured by the one or more cameras to indicate a fourth amount of time, less than the third amount of time.
 17. The computer system of claim 1, wherein the recording space affordance is displayed while capture of media via the one or more cameras is not occurring.
 18. The computer system of claim 1, wherein the recording space affordance is displayed while capture of media via the one or more cameras is occurring.
 19. The computer system of claim 18, including, during ongoing capture of media with the one or more cameras of the device: while the recording space affordance is not displayed, determining that the recording space available for recording media captured by the one or more cameras has fallen below a third threshold amount; and in response to determining that the recording space available for recording media captured by the one or more cameras has fallen below the third threshold amount, displaying the recording space affordance.
 20. The computer system of claim 1, wherein the recording space affordance is overlaid on the camera preview.
 21. The computer system claim 1, wherein displaying the camera user interface includes displaying, concurrently with the camera preview and the recording space affordance, a media capture affordance that, when selected, initiates capture of media via the one or more cameras.
 22. The computer system of claim 21, the one or more programs further including instructions for: receiving, via the one or more input devices, input corresponding to the media capture affordance; and in response to receiving the input corresponding to the media capture affordance, initiating the capture of media via the one or more cameras.
 23. The computer system of claim 1, the one or more programs further including instructions for: displaying, in the camera user interface, a media capture affordance: in accordance with a determination that the recording space available for recording media captured by the one or more cameras is above a fourth threshold amount, displaying the media capture affordance in a first visual state, wherein the media capture affordance is selectable while in the first visual state; and in accordance with a determination that the recording space available for recording media captured by the one or more cameras is below the fourth threshold amount, displaying the media capture affordance in a second visual state, wherein the media capture affordance is not selectable while in the second visual state.
 24. The computer system of claim 23, the one or more programs further including instructions for: while the media capture affordance is displayed in the second visual state, determining that the amount of recording space available for recording media captured by the one or more cameras has increased above the fourth threshold amount; and in response to determining that the amount of recording space available for recording media captured by the one or more cameras has increased above the fourth threshold amount, updating the media capture affordance from the second visual state to the first visual state.
 25. The computer system of claim 23, the one or more programs further including instructions for: while the media capture affordance is displayed in the second visual state, detecting a request to modify one or more media capture settings; and in response to detecting the request to modify the one or more media capture settings: modifying the one or more media settings, wherein modifying the one or more media settings reduces the bitrate of captured media; and updating the media capture affordance from the second visual state to the first visual state.
 26. The computer system of claim 1, wherein displaying the camera user interface includes displaying, concurrently with the camera preview and the recording space affordance, a set of one or more media capture setting affordances.
 27. The computer system of claim 26, wherein the set of one or more media capture setting affordances includes a first media capture setting affordance that, when selected, changes the media capture bitrate.
 28. The computer system of claim 26, wherein the set of one or more media capture setting affordances includes two or more different media capture setting affordances independently selected from the group consisting of: a media capture setting affordance that modifies a media codec setting, a media capture setting affordance that modifies a frame rate setting, and a media capture setting affordance that modifies a pixel density setting.
 29. The computer system of claim 1, the one or more programs further including instructions for: while the computer system is in a third media capture mode and while the recording space affordance is not displayed, detecting a request to transition to a fourth media capture mode; and in response to the request to transition to the fourth media capture mode: transitioning to the fourth media capture mode; and displaying the recording space affordance.
 30. The computer system of claim 1, the one or more programs further including instructions for: displaying a second camera user interface, wherein displaying the second camera user interface includes: in accordance with a determination that the recording space available for recording media captured by the one or more cameras is below a fifth threshold amount, displaying the camera preview concurrently with the recording space affordance; and in accordance with a determination that the recording space available for recording media captured by the one or more cameras is above the fifth threshold amount, displaying the camera preview without the recording space affordance.
 31. The computer system of claim 30, wherein displaying the camera preview without the recording space affordance includes displaying, concurrently with the camera preview, a second indication of an amount of time available to record and store, in the recording space, media captured by the one or more cameras.
 32. The computer system of claim 30, wherein the recording space affordance, when displayed in the second camera user interface, is displayed at a first location in the second camera user interface, the one or more programs further including instructions for: while displaying the second camera user interface, receiving, via the one or more input devices an input corresponding to the first location; and in response to receiving the input corresponding to the first location: in accordance with a determination that the recording space affordance is currently displayed in the second camera user interface, performing the operation associated with changing an amount of recording space available for recording media captured by the one or more cameras; and in accordance with a determination that the recording space affordance is not currently displayed in the second camera user interface, performing a camera operation that does not include performing the operation associated with changing an amount of recording space available for recording media captured by the one or more cameras.
 33. The computer system of claim 1, wherein the recording space affordance is displayed concurrently with an indication of an additional amount of time available to record and store, in the recording space, media captured by the one or more cameras that would be made available by performing the operation associated with changing an amount of recording space available for recording media captured by the one or more cameras.
 34. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system having one or more cameras and that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: displaying, via the display generation component, a camera user interface, wherein displaying the camera user interface includes concurrently displaying: a camera preview that includes a representation of one or more objects in a field-of-view of a first camera of the one or more cameras; and a recording space affordance that, when selected, initiates performing an operation associated with recording space available for recording media captured by the one or more cameras; receiving, via the one or more input devices, input corresponding to selection of the recording space affordance; and in response to receiving the input corresponding to selection of the recording space affordance, performing the operation associated with changing an amount of recording space available for recording media captured by the one or more cameras.
 35. A method, comprising: at a computer system having one or more cameras, wherein the computer system is in communication with a display generation component and one or more input devices: displaying, via the display generation component, a camera user interface, wherein displaying the camera user interface includes concurrently displaying: a camera preview that includes a representation of one or more objects in a field-of-view of a first camera of the one or more cameras; and a recording space affordance that, when selected, initiates performing an operation associated with recording space available for recording media captured by the one or more cameras; receiving, via the one or more input devices, input corresponding to selection of the recording space affordance; and in response to receiving the input corresponding to selection of the recording space affordance, performing the operation associated with changing an amount of recording space available for recording media captured by the one or more cameras. 